Mobile communication device dynamic service application and dynamic service application scripting

ABSTRACT

A dynamic service application is stored and executed on a mobile or wireless communication device (e.g., a cellular telephone) to enable it to be programmed without specialized hardware, software, and other proprietary information. For example, dynamic service application programs or scripts may be entered directly by a user or may be received as a wireless or radiated digital message transmission. The dynamic service application executes the dynamic service application script, which is of a format to accommodate wireless or radiated transmission and storage on the device. The dynamic service application script may be written directly by a user on a computer or a mobile communication device or may be written with the aid of scripting “wizard” software that runs on a computer and guides the writing of script without the user having to work directly with the dynamic service application script. In addition to being received as radiated transmissions, dynamic service application scripts may also be sent as radiated transmissions from mobile communication devices to other devices or computers.

SUMMARY OF THE INVENTION

The present invention relates to mobile or wireless communicationdevices, including digital cellular telephones, and in particular to ashort text message dynamic service application for such devices.

Programming small mobile or wireless communication devices, like digitalcellular telephones phones, typically requires specialized hardware orsoftware, or access to proprietary information like authentication keys,codes, etc. As a consequence, it is typically difficult or impossiblefor end-users to program such mobile devices. As is known in the art,digital cellular telephones of the GSM-type include removable SubscriberIdentity Modules (SIMs), which are sometimes called smart cards or chipcards. To program a GSM cellular telephone, for example, it is necessaryto use a smart card programming device and a smart card programmingtoolkit, and to access the account authentication key, the last of whichis typically not accessible except by wireless service providers. Theinability of users to program or modify mobile or wireless communicationdevices limits the versatility and usefulness of such devices.

Accordingly, the present invention includes a dynamic serviceapplication that is stored and executed on a mobile or wirelesscommunication device to enable it to be programmed without specializedhardware, software, and other proprietary information. For example, thedynamic service application may be distributed with or stored on thewireless device in a conventional manner, but dynamic serviceapplication programs or scripts may be entered directly by a user or maybe received as a wireless or radiated digital message transmission. Incontrast, conventional programming of such a device requires a direct orconductive hardware coupling to the device.

The dynamic service application executes the dynamic service applicationscript, which is of a format that accommodates wireless or radiatedtransmission and storage on the device. The dynamic service applicationscript may be written directly by a user on a computer or a mobilecommunication device or may be written with the aid of scripting“wizard” software that runs on a computer and guides the writing ofscript without the user having to work directly with the dynamic serviceapplication script. In addition to being received as radiatedtransmissions, dynamic service application scripts may also be sent asradiated transmissions from mobile communication devices to otherdevices or computers.

In one exemplary implementation, a dynamic service application of thepresent invention may be stored on a SIM or smart card for use in anassociated GSM cellular telephone. Dynamic service application scriptsmay be received at and sent from the GSM cellular telephone as shorttext message dynamic service scripts that conform to the short messageservice (SMS) format for GSM cellular telephones. In communicating witha conventional (e.g., desktop) computer, the scripts may be prepared andsent or received and run by software operating locally on the computeror at a site on the global computer network (e.g., a Web site).

The dynamic service application interprets and executes short textmessage dynamic service scripts that the cellular telephone receives,whenever the scripts are supported by a service present on the cellulartelephone. The contents of the short text message dynamic service scriptcould be either a new application, a part of the application (e.g.,applications could be broken into segments), an application update, acommand to execute, or data for a particular application. The user canalso send messages from the phone to the web site. These messages can bedistributed to other users as needed.

Additional objects and advantages of the present invention will beapparent from the detailed description of the preferred embodimentthereof, which proceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a GSM cellular telephone as an exemplary mobilewireless communication device operating environment for an embodiment ofthe present invention.

FIG. 2 is a block diagram illustrating operation of a short messageservice (SMS) system compatible with transmission of short text messagedynamic service scripts of the present invention.

FIG. 3 is a flow diagram of a mobile device dynamic service methodaccording to the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention relates to mobile or “wireless” communicationdevices capable of transmitting and/or receiving radiated (i.e.,wireless) fixed length text messages of up to a maximum fixed length.Such communication devices may be implemented with various functions andin numerous forms including digital cellular telephones, portable andhandheld computers, personal digital assistants, etc. The invention isdescribed in reference to a digital cellular telephone, but is similarlyapplicable to other mobile or wireless communication devices thattransmit and/or receive radiated fixed length text messages.

FIG. 1 illustrates a GSM cellular telephone 10 as an exemplary mobilewireless communication device operating environment for an embodiment ofthe present invention. GSM cellular telephone 10 may conform, forexample, to the European Telecommunications Standards Institute (ETSI)specifications GSM 11.11 and GSM 11.14 for Global Systems for Mobilecommunications. It will be appreciated, however, that GSM cellulartelephone 10 could instead conform to another communication standard ora standard not yet developed, such as the ETSI 3rd Generation MobileSystem standard that is sometimes referred to as the Third GenerationPartnership Project or “3GPP”.

GSM cellular telephone 10 includes a removable Subscriber IdentityModule (SIM) 12, which is sometimes called a smart card or chip card.For example, SIM 12 can be of a smart card format that has thewell-known size of credit cards (e.g., standardized dimensions of 53.98mm×85.60 mm×0.76 mm), or can be of a smaller format that is sometimescalled a “plug-in SIM”. SIM 12 includes a medium 14 that supports a SIMelectronic circuit 16 (e.g., one or more semiconductor integratedcircuits or chips). Medium 14 typically includes multiple laminatedsynthetic layers, with one or more internal layers being between outerlayers. SIM electronic circuit 16 is incorporated into or on at leastone of the internal layers.

SIM electronic circuit 16 includes a central processing unit or CPU 20(e.g., a microprocessor or microcontroller) in conjunction with a memorysystem 22, a data transmit interface 24, and a data receive interface26, all of which are interconnected by a bus structure 28. Similarly,GSM cellular telephone 10 includes a central processing unit or CPU 30(e.g., a microprocessor or microcontroller) in conjunction with a memorysystem 32, a data transmit interface 34, and a data receive interface36, all of which are interconnected by a bus structure 38. In addition,GSM cellular telephone 10 includes a system display 40 and a user inputdevice or keypad 42, as well as a power supply (e.g., a battery),telephonic audio input and output elements, and radio frequencytransmitting and receiving elements that are not shown.

While SIM electronic circuit 16 includes the basic elements of a simplecomputer, neither SIM 12 nor SIM electronic circuit 16 is capable offunctioning as a stand-alone computer. Neither SIM 12 nor SIM electroniccircuit 16 includes a power source nor user interface components bywhich a user could interact with SIM 12 or SIM electronic circuit 16.The computer functionality of SIM 12 can be accessed only by connectingit to another computer, such as GSM cellular telephone 10 or a SIMreader that is connected to a personal computer, as is known in the art.When connected to another computer, such as GSM cellular telephone 10,SIM 12 is powered and communicates through its interfaces 24 and 26 toreceive data from and provide data to the other computer.

As is common, GSM cellular telephone 10 supports a fixed length textmessage service by which radiated (i.e., wireless) fixed length textmessages of up to a maximum fixed length may be transmitted or receivedby GSM cellular telephone 10. As an example, the fixed length textmessage service could include or conform to the short message service(SMS) standard that is part of the GSM Phase 1 standard. The SMSstandard allows transmission of radiated fixed length text messages ofup to 160 characters in length. Such a fixed length text message servicemay be distinguished from conventional network connections or servicesin which files of generally arbitrary size may be transmitted. Whilereferring to transmission of SMS messages, the following description maybe similarly applicable to other standards or formats for radiated fixedlength text messages.

FIG. 2 is a block diagram illustrating operation of a SMS system 50 fortransmitting SMS messages from any of transmitting short messageterminals 54 to a receiving short message terminal 56, which may beimplemented as GSM cellular telephone 10.

For purposes of simplicity, this illustration is directed tocommunication in only direction: from transmitting short messageterminal 54 to receiving short message terminal 56. It will beappreciated that each of short message terminals 54 and 56 wouldtypically be capable of bi-directional communication so that thefollowing description would be similarly applicable to communicationfrom terminal 56 to any or all of terminals 54.

Transmitting short message terminal 54 may be any text-capable digitaldevice, including a computer (e.g., desktop, portable, handheld, server,etc.), a personal digital assistant, a digital telephone, a digitalcellular telephone, etc. An SMS message created at transmitting shortmessage terminal 54 is transmitted over a communication channel 58 to ashort message service center or message center 60 that functions as astore and forward center for transmitting SMS messages between shortmessage terminals. For example, message center 60 receives a SMS messagefrom transmitting short message terminal 54 and stores the SMS messageuntil it can be forwarded to receiving short message terminal 56.Message center 60 then transmits the SMS message to receiving shortmessage terminal 56 over a communication channel 62.

In view of the variety of devices that can function as message terminals54 and 56, communication channels 58 and 62 may be or include any publicor private computer network (e.g., the global computer network calledthe Internet) or any telephone network (e.g., any PSTN or any cellularor other wireless communication network). With receiving short messageterminal being GSM cellular telephone 10 in the illustrated example,communication channel 62 will include at least a GSM cellular telephonenetwork.

FIG. 3 is a flow diagram of a mobile device dynamic service method 100according to the present invention. In one implementation, mobile devicedynamic service method 100 is performed by various elements of SMSmessage system 50, including a dynamic service application stored on SIM12. It will be appreciated that in other implementations, the dynamicservice application may be stored or executed on any part of a shortmessage terminal 54 or 56.

Process block 102 indicates that a short text message dynamic servicescript is formed. In one implementation, the short text message dynamicservice script may conform to the SMS message format associated with GSMcellular telephones.

Process block 104 indicates that the short text message dynamic servicescript is transmitted to a receiving short message terminal. Forexample, the short text message dynamic service script could betransmitted via a message center 60 to GSM cellular telephone 10.

Process block 106 indicates that the short text message dynamic servicescript is interpreted and executed by the dynamic service application.Interpretation of the short text message dynamic service script by thedynamic service application includes correlating operations indicated bythe short text message dynamic service script with the correspondingapplication programming interfaces (APIS) and any other resourcesavailable from SIM 12. For example, one option is to save the script andadd the application name to the cellular telephone.

Process block 108 indicates that the short text message dynamic servicescript is received and stored, such as on a SIM 12 of a GSM cellulartelephone 10.

Process block 110 indicates that the short text message dynamic servicescript is executed, such as on a SIM 12 of a GSM cellular telephone 10.

The short text message dynamic service scripts functions as short textmessage applications and can be formed in a variety of ways. As oneexample, a user could write a short text message application directly inaccordance with a scripting notation, as described below in greaterdetail. As another example, a user may be guided through a scriptformation process or “wizard” that is accessed from a personal computer.The script formation process or “wizard” may be run locally on thepersonal computer or may be accessed from a network site (e.g., a Webpage) on the global computer network.

Set forth below are exemplary steps through which scripting wizardsoftware could direct a user creating a short text message dynamicservice script or application. The exemplary steps could be offered orpresented to the user in different sequences according to choices orselections made by the user. Once each branch or segment of theapplication is completed, the scripting wizard software codes andencrypts the application so that it can be sent to the receiving mobilecommunication device (e.g., GSM cellular telephone 10) as one or moreshort text messages (e.g., SMS messages). Once it receives the one ormore short text messages, the dynamic service application on the mobilecommunication device interprets it or them and executes the steps asspecified in the script. As an example, one option is to save the scriptand add the application name to the mobile communication device (e.g.,cellular telephone).

User selects application options:

1. Specify application name and various application properties

-   -   A. Name    -   B. Description    -   C. Access (Publish/don't publish in directory service)    -   D. Membership (Members only/open to public)    -   E. Author information

2. Execute on the cell phone only once

-   -   A. Manually (application is added to the phone app menu and        deleted after execution)    -   B. Upon receipt of SMS message    -   C. With a delay after receiving SMS message    -   D. At a specified time, date    -   E. Triggered with events

3. Execute on the cell phone more than once

-   -   A. Manually (application is added to the phone app menu)    -   B. With specified interval    -   C. At specified time(s), date(s)    -   D. Triggered with events

User selects initial interaction type between the application and thecell phone user after the application is launched.

Examples of operations:

1. Show selection list (user is required to select item(s) from a list)

-   -   A. Enter text describing the list    -   B. Enter items of the list    -   C. Specify operation(s) to execute upon selection of an item        (each item may be associated with a different operation that        follows)

2. Show “edit box” (user is required to enter text)

-   -   A. Enter text describing the edit box (description of the text        to be entered).    -   B. (Optional) Enter a text string that triggers a specific        operation and specify this operation.    -   C. (Optional) Additional specification(s) as in B.    -   D. (Optional) Specify operation(s) to execute after any other        non-empty text is entered.

3. Print text

-   -   A. Specify text to be printed    -   B. Specify delay time before continuing, or manual continuation    -   C. Specify conditions under which this operation (print text)        will or will not execute (time, location, . . . ). Execution        continues with the following operation (C)    -   D. (Optional) Specify operation to execute after text is        printed.

4. Play tone

-   -   A. Specify tone parameters (type of tone, length, etc)

5. Send message/command to specified destination(s)

-   -   A. Specify message/command    -   B. (Optional) Specify operation to execute after message/command        is successfully sent    -   C. (Optional) Specify operation to execute after sending        message/command failed.

6. File operation

-   -   A. Clear    -   B. Delete    -   C. Delete Item    -   D. Append

Selected aspects of a first implementation of a format of a short textmessage dynamic service script are described below with reference to anexemplary script. It will be appreciated that this exemplary script isprovided merely to illustrate the various script elements and does notinclude all potential elements in the script format or the full range ofpotential functionality that can be provided by the script format.

In this implementation, a typical script includes a file or variablewith multiple successive statements that each may include one or morescript elements. The successive statements of a script may form one ormore files that are each no larger than the basic memory buffer size fora receiving mobile or “wireless” communication device (e.g., 128 bytesfor a SIM), thereby allowing a complete script file to be completelycontained in the memory buffer. In the illustrated exemplary script,different statements are initiated by the terms Start, Efopen, Cont1,Iter, Cont2, which may be referred to as the statement names.

Start: !gEFopen oF1“/Pgm/SV.m” gCont1 EFopen: T1=“Error opening file ”T1<T0<“ (“<hIE<”)” pT1 q Cont1: T2=“T1=s” !gCont2 I1=0 Iter:T2<“,”<h22<F1(I1, 11)<h22 I1+16 gIter Cont2: T2<“q;” !q cF1 xT2 tT1T2=“/Pgm/” T2<T1 T2<“.a” oF1T2 xF1 q

In this implementation, script elements are generally represented byonly one or two alphanumeric characters to minimize the script size, andoperators are indicated by lower case letters. For example, the Startstatement begins with an error handling indicator “!” that is coupledwith a get element “g” and a statement name “EFopen.” This scriptelement combination is interpreted and executed by the dynamic serviceapplication as follows: if an error arises (!), get (g) the indicatedstatement (EFopen). The get element g may have as its argument anystatement name in a file, a file name, a memory location pointer, etc.Accordingly, the get element g functions as a versatile program controldevice for directing script execution toward a variety of elements.

The EFopen statement sets a text variable (T1) to a text string “Erroropening file,” and the element T1<T0< “(“<hIE<”)” functions to append atext variable T0 and the text “(32)” (where the value of 32 is anexample value of the file handle, hIE) to text variable T1, with thetext variable T0 being a temporary buffer having the value of _the filename (last statement's text). Element pT1 functions to print (p) (i.e.,display) the error indication specified for variable T1 (i.e., textstring “Error opening file”), and the quit element (q) ends execution ofthe script.

In the absence of an error indication by the executing mobile device,the Start statement proceeds to the script element oF1“/Pgm/SV.m”, whichopens (o) as a file variable (F1) the file SV.m stored on the device insubdirectory Pgm. The .m extension may indicate that the file SV.m is alisting or menu of available script or application files available inthe Pgm subdirectory. The script element gCont1 then gets (g) statementCont1. The file variable (F1 ) represents a file-type variable that canbe indexed over a range of values to support file operations (e.g.,open, o). This script format implementation also includes, for example,an indexed text variable (e.g., T1) and an indexed numeric or numericvariable (e.g., I1) to support text and integer operations,respectively.

In the Cont1 statement, script element T2=“T1=s”sets a text variableindex T2 to the indicated text string (T1=s). Script element !gCont2directs the script to get or goto (g) statement Cont2 in case of anerror indication. Script element I1=0 sets a value of zero to theinteger variable I1.

In the absence of an error indication in it, statement Cont1 proceeds tostatement Iter, which functions as an iteration operation. Scriptelement T2<“,”<h22<F1(I1, 11)<h22 appends to text variable T2 a comma, aquote (by operation of element h22), 11 characters at iteration variablelocation I1 in file F1, and another quote (by operation of element h22).Element I1+16 is an integer operation adding variable I1 and the number16. Element gIter repeats operation of statement Iter for anotheriteration. For example, each address location in a file could include 16character positions, so this script element would function to obtain thefirst 11 characters at each address location in file F1.

In the Cont2 statement, element T2<“q;” appends a quit operator to textvariable T2. As a result, of the operation of statements Iter and Cont2,variable T2 includes the following elements:T2:T1=s,F1(0,11), F1(1,11), . . . , q;in which the elements F1(0,11), F1(1,11), . . . include the 11 charactertext strings at locations 0, 1, . . . in file F1. The 11 characteriteration may reflect that the mobile communication device displays 11characters per line. Script element cF1 closes (c) file F1, and scriptelement xT2 executes (x) variable T2, in which the select element sfunctions to display each text string F1(1,11) so a user can select oneof them. Script element tT1 trims spaces at the beginning and at the endof the text. The script elements T2=“/Pgm/”, T2<T1, and T2<“.a”setvariable T2 to the subdirectory and application name and extension (.a)of the application selected by the user. Script element oF 1T2 opens asfile F1 the specified file, and element ×F1 executes it.

The exemplary script functions to display a list of text messageapplications available on a mobile communication device and to allow auser to select and execute one of the applications. It will beappreciated that such an application would typically requiresignificantly greater memory and syntax resources if it were written ina conventional scripting language.

Selected aspects of a second implementation of a short text messagedynamic service script format are described below. This secondimplementation includes more programming specificity than the first, butdisadvantageously increases the memory requirements of the dynamicservice application.

-   Message consists of two components: <MSGHEADER><COMMANDS>-   <MSGHEADER>: <MSGID><MSGOPTS>/<APPNAME>-   <MSGID>—Message ID for this recipient (cell phone, web site),    sequence 0, 1, 2, 3, . . . (only decimal digits)-   <MSGOPTS>—Message options    -   A—ACK of the message with MSGID following (eg. A123)    -   R—ACK of this message requested    -   I—Install as application. <COMMANDS> are stored in a file, added        to apps menu, and executed by the user. Otherwise <COMMANDS> are        executed upon receipt of the message.    -   C<item>-<Of>—Not complete message. This is item <Item> of <Of>        items. The contents of this message is appended to already        loaded chunks.-   <APPNAME>—Name of the application represented by the message    contents    Example: 98I/Nearby-   <COMMANDS> consists of a set of <CMD><CMDOPT>/<CMDBODY> separated    with ‘&’    -   <CMD>—Command:        -   S—Select item from the list of items in the <CMDBODY>            separated with ‘/’        -   The text before the first ‘/’ after <CMDOPT> is the            description of the items to select. If it is empty            (<CMD><CMDOPT>// . . . ) then the text “Select:” is printed.    -   <CMDOPT> (all optional):        -   A—append to clipboard        -   T—the result is text of the selected item instead of index            (1, 2, . . . )        -   E<CMDID>—error handler—command to execute next on error.            -   <CMDID> specifies which command to execute (1, 2, . . .                )    -   Result: Selected item. Result is appended to the clipboard    -   Notes: All items are separated with ‘/’ and optionally,        following the separator is a number that specifies a command ID        of a command to execute if this item is selected.    -   The first item is the title of the selection with optional        preceding default command ID.    -   Examples:        -   S/Where?/My Office/Room 123/Park        -   SML1E13A/15Where?/12My Office/14Room 123/15Park-   E—Enter value (text) for the text described in the body.-   <CMDOPT>/<CMDID><Text>[/<CMDID><Text>/<CMDID><Text>. . . ]-   <CMDOPT> (all optional):    -   L—Allow letters and digits    -   A—Append to clipboard    -   T—append to text the clipboard, save clipboard    -   C—Set clipboard (default)    -   D—Allow to enter decimal digits only    -   N—specifies minimum size of input (followed by size)    -   X—specifies maximum size of input (followed by size)    -   E<CMDID>—error handler—command to execute next on error.        -   <CMDID> specifies which command to execute (1, 2, . . . )

Result: Entered item text. Result is added to the clipboard depending onthe options specified.

Notes:

-   -   The body of the command may consist of a list of items separated        with ‘/’ with preceding command ID of a command to execute if        this item is entered.    -   The first item is the title of the edit box with optional        preceding default command ID (command to be executed next).        Examples:    -   E/Enter your name    -   EX8N3E13A/31Enter your name:/01Cezary/02Harry/03Lili/04 007

-   P—Print text <CMDOPT>/<CMDID><Text>    -   <CMDOPT>:        -   T—Append to the text content of the clipboard and print the            result        -   C—Append the specified text to the clipboard and print the            result        -   E<CMDID>—error handler—command to execute next on error.            -   <CMDID> specifies which command to execute (1, 2, . . .                )

Result: Printed text. Result is appended to the clipboard if T nor Cspecified. If option T is specified the clipboard contains the printedtext.

Examples:

-   -   P/Hello World!    -   PTE13/Hello World!

-   F—File operation    -   <CMDOPT> (One of C, A, O, D required):        -   C—Append the content of the specified file to the clipboard        -   A—Append the text of the clipboard to the specified file        -   O—Overwrite the content of the file with the content of            clipboard        -   D—Delete specified file        -   B—Treat file as binary        -   E<CMDID>—error handler—command to execute next on error.            -   <CMDID> specifies which command to execute (1, 2, . . .                )                Examples:    -   FC/“/Pgm/Test.data”    -   FBOE13/“/7F20/6F74”

-   C—Clipboard operation—set the content to the specified text    <CMDOPT>/<ContCommandlD><Text>    -   -   T—Append to the text content of the clipboard and store the            result        -   C—Clear the contents        -   A—Append the specified text (instead of setting the value)        -   E<CMDID>—error handler—command to execute next on error.            -   <CMDID>specifies which command to execute (1, 2, . . . )                Examples:

    -   C/Hello World!

    -   CAE13/Hello World!        Examples:

-   &P/Hello World!!!

-   &C/Hello . . . &PC/from clipboard!!!

-   &C/hello!!!&PT/From clipboard

-   &C/Hello &EA/Enter your name:&PC/,good to see you!

In accordance with the practices of persons skilled in the art ofcomputer programming, the present invention is described above withreference to acts and symbolic representations of operations that areperformed by various computer systems, including mobile communicationdevices and “smart cards.” Such acts and operations are sometimesreferred to as being computer-executed and may be associated with theoperating system or the application program as appropriate. It will beappreciated that the acts and symbolically represented operationsinclude the manipulation by a CPU of electrical signals representingdata bits, which causes a resulting transformation or reduction of theelectrical signal representation, and the maintenance of data bits atmemory locations in a memory system to thereby reconfigure or otherwisealter the computer system operation, as well as other processing ofsignals. The memory locations where data bits are maintained arephysical locations that have particular electrical, magnetic, or opticalproperties corresponding to the data bits.

Having described and illustrated the principles of our invention withreference to an illustrated embodiment, it will be recognized that theillustrated embodiment can be modified in arrangement and detail withoutdeparting from such principles. It should be understood that theprograms, processes, or methods described herein are not related orlimited to any particular type of computer apparatus, unless indicatedotherwise. Various types of general purpose or specialized computerapparatus may be used with or perform operations in accordance with theteachings described herein. Elements of the illustrated embodiment shownin software may be implemented in hardware and vice versa.

In view of the many possible embodiments to which the principles of ourinvention may be applied, it should be recognized that the detailedembodiments are illustrative only and should not be taken as limitingthe scope of our invention. Rather, we claim as our invention all suchembodiments as may come within the scope and spirit of the followingclaims and equivalents thereto.

1. A mobile device dynamic service method in a mobile digitalcommunication device, comprising: reception of a radiant transmission ofa script program by the mobile digital communication device wherein thescript program is a short text message dynamic service script program;storage of the script program on the mobile digital communication devicefor execution at a time delayed from a time of reception; addition of anapplication name in the mobile digital communication device, theapplication name representing the script program; and interpretation andexecution of the script program by a dynamic service applicationoperating on the mobile digital communication device wherein the dynamicservice application is operable to support a short text message dynamicservice script program comprising variables, operators, program controlelements, error indicators, iteration, and displaying information ofsaid script via the mobile digital communication device, wherein themobile digital communication device includes an account authenticationkey and wherein the short text message dynamic service script programconforms to short message service (“SMS”) format.
 2. The method of claim1 in which the mobile digital communication device includes a subscriberidentity module that is removable from the mobile digital communicationdevice and in which the dynamic service application is stored on thesubscriber identity module.
 3. The method of claim 1 in which the mobiledigital communication device includes a subscriber identity module thatis removable from the mobile digital communication device and in whichthe dynamic service application is stored and executed on the subscriberidentity module.
 4. The method of claim 1 in which the short textmessage dynamic service script program is stored on the mobile digitalcommunication device for execution thereon more than once.
 5. The methodof claim 1 in which execution of the short text message dynamic servicescript program on the mobile digital communication device includesobtaining information from an operator of the mobile digitalcommunication device.
 6. The method of claim 1, wherein the mobiledigital communication device is a digital cellular telephone.
 7. Themethod of claim 1, wherein the time delayed from a time of receptionindicates a specific time and date of execution.
 8. The method of claim1, wherein the mobile digital communication device includes a subscriberidentity module that is removable from the mobile digital communicationdevice, wherein the storage of the script program includes storage ofthe script program on the subscriber identity module.
 9. A mobiledigital communication device configured to receive radiant transmissionof short text messages, the device comprising: a dynamic serviceapplication configured to receive a radiantly transmitted script programand interpret and execute the script program on the mobile digitalcommunication device via an Application Programming Interface (“API”);an application name added to the mobile digital communication device theapplication name representing the script program; and a subscriberidentity module that is removable from the mobile digital communicationdevice and that is configured to perform executable operations thatcomprise the API, wherein the dynamic service application is operable tosupport a short text message dynamic service script program comprisingvariables, operators, program control elements, error indicators,iteration, and displaying information of said script via the mobiledigital communication device, and wherein the mobile digitalcommunication device includes an account authentication key and whereinthe short text message dynamic service script program conforms to shortmessage service (“SMS”) format.
 10. The device of claim 9 in which thedynamic service application is stored on the subscriber identity module.11. The device of claim 9 in which the dynamic service application isstored and executed on the subscriber identity module.
 12. The device ofclaim 9 in which the short text message dynamic service script programis stored on the mobile digital communication device for executionthereon more than once.
 13. The device of claim 9 in which execution ofthe short text message dynamic service script program on the mobiledigital communication device includes obtaining information from anoperator of the mobile digital communication device.
 14. The device ofclaim 9, wherein the mobile digital communication device is a digitalcellular telephone.